-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix OOM (Out Of Memory) Errors #138
base: main
Are you sure you want to change the base?
Conversation
Thank you for your contribution @mjnaderi ! |
@@ -8,7 +8,7 @@ services: | |||
restart: ${RESTART_POLICY} | |||
security_opt: | |||
- no-new-privileges:true | |||
pids_limit: 100 | |||
pids_limit: 200 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no need to change the limit for postgres.
@@ -31,7 +31,7 @@ services: | |||
restart: ${RESTART_POLICY} | |||
security_opt: | |||
- no-new-privileges:true | |||
pids_limit: 200 | |||
pids_limit: 400 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More than 200 processes means that something is very wrong with the system. I'd like to get a list of the processes if possible and see if there's an actual bug from the product that needs to be fixed. Otherwise, there's a chance that we are hiding something under the rug here.
Thanks for the input Agniva! Agreed, if more than 200 PIDs is an unreasonable number then we'd better understand what that is first before thinking about merging this change. |
We first need to understand why there is a spike in PIDs
I had the same problem and changing this values fixed it. |
Did you try listing out the processes to see what was wrong? |
No, but since then, I did not have any crashes, so I did not have the chance to |
Summary
This PR fixes mattermost/mattermost#20625.
Ticket Link
None